chore(data): weekly link freshness pass - #23
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by
.github/workflows/link-freshness.yml.tools/check-links.mjsprobed every URL in every column, followedredirects, and rewrote the rows whose URL now resolves somewhere else.
Dead URLs are deliberately not touched. A 404 has no known
replacement and inventing one would put a fabrication in the dataset;
they are listed in
datasets/link-health.jsonunderfindingswith"outcome": "dead"for a human to resolve.403and429are recorded asblocked, notdead— being refusedby a bot-detecting CDN says nothing about whether the page exists, so
those never drive a correction either.
Per-run totals are appended to
datasets/link-health-history.csv.The series is the interesting output; a single snapshot is not.